V1.0 October 24, 2017 document name userguide
Content Changes
|
Version |
Date |
Description |
Revised by |
Approved by |
|
|
|
|
|
|
|
|
|
|
|
|
Contents
1.3 Definitions, acronyms,
and abbreviations
[Introduce the product and its purpose,
highlighting key features and benefits].
[Introduce the purpose of the user guide, what
functionality or workflows will be covered? Are there any assumptions about the
users’ knowledge or experience, or prerequisites? ]
|
Definition |
|
|
|
|
|
|
|
|
|
|
[Provide a concise description of the
context for this sub-process or workflow, including any requirements or
conditions that are relevant.]
[If a sub-process or workflow step
requires additional context and detailed information to properly prepare the
user, you can expand a context section to include tables (such as definitions
of the values available in a dropdown) or graphics such as flow diagrams.
[Appendices are optional, and are used to provide additional detailed
information that may help the end user manage the overall application. Examples
could include references to standards (such as W3C standards), technical
specifications required for regulatory compliance, checklists, or other
information of a technical nature.]